This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @jfreden? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b add_slowlog_user_data upstream/add_slowlog_user_data
git merge upstream/main
git push upstream add_slowlog_user_data

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

💚 Build Succeeded

• Buildkite Build
• Commit: 94c9871

History

• 💚 Build #3531 succeeded 04b46c6
• 💚 Build #3524 succeeded cc31660
• 💚 Build #3519 succeeded 36ee90c
• 💚 Build #3515 succeeded b23ea7b
• 💚 Build #3489 succeeded 3ec53c5
• 💚 Build #3465 succeeded 6d217d7

cc @jfreden

💚 Build Succeeded

• Buildkite Build
• Commit: 94c9871

History

• 💚 Build #1476 succeeded 04b46c6
• 💚 Build #1469 succeeded cc31660
• 💚 Build #1464 succeeded 36ee90c
• 💚 Build #1460 succeeded b23ea7b
• 💚 Build #1434 succeeded 3ec53c5
• 💚 Build #1410 succeeded 6d217d7

cc @jfreden

💚 Build Succeeded

• Buildkite Build
• Commit: 94c9871

History

• 💚 Build #1041 succeeded 04b46c6
• 💚 Build #1034 succeeded cc31660
• 💚 Build #1029 succeeded 36ee90c
• 💚 Build #1025 succeeded b23ea7b
• 💔 Build #999 failed 3ec53c5
• 💔 Build #975 failed 6d217d7

cc @jfreden

💚 Build Succeeded

• Buildkite Build
• Commit: 94c9871

History

• 💚 Build #2313 succeeded 04b46c6
• 💚 Build #2306 succeeded cc31660
• 💚 Build #2301 succeeded 36ee90c
• 💚 Build #2297 succeeded b23ea7b
• 💚 Build #2271 succeeded 3ec53c5
• 💚 Build #2247 succeeded 6d217d7

cc @jfreden

💚 Build Succeeded

• Buildkite Build
• Commit: 94c9871

History

• 💚 Build #2320 succeeded 04b46c6
• 💚 Build #2313 succeeded cc31660
• 💚 Build #2308 succeeded 36ee90c
• 💚 Build #2304 succeeded b23ea7b
• 💚 Build #2278 succeeded 3ec53c5
• 💚 Build #2254 succeeded 6d217d7

cc @jfreden

💚 Build Succeeded

• Buildkite Build
• Commit: 94c9871

History

• 💚 Build #1051 succeeded 04b46c6
• 💚 Build #1044 succeeded cc31660
• 💚 Build #1039 succeeded 36ee90c
• 💚 Build #1035 succeeded b23ea7b
• 💔 Build #1009 failed 3ec53c5
• 💔 Build #985 failed 6d217d7

cc @jfreden

💚 Build Succeeded

• Buildkite Build
• Commit: 94c9871

History

• 💚 Build #1083 succeeded 04b46c6
• 💚 Build #1076 succeeded cc31660
• 💚 Build #1071 succeeded 36ee90c
• 💚 Build #1067 succeeded b23ea7b
• 💔 Build #1041 failed 3ec53c5
• 💔 Build #1017 failed 6d217d7

cc @jfreden

💚 Build Succeeded

• Buildkite Build
• Commit: 94c9871

History

• 💚 Build #1038 succeeded 04b46c6
• 💚 Build #1031 succeeded cc31660
• 💚 Build #1026 succeeded 36ee90c
• 💚 Build #1022 succeeded b23ea7b
• 💚 Build #996 succeeded 3ec53c5
• 💚 Build #972 succeeded 6d217d7

cc @jfreden

💔 Build Failed

• Buildkite Build
• Commit: 94c9871

Failed CI Steps

• :windows:-family/core-windows-2016 Unit Tests
• :windows:-family/core-windows-2022 Unit Tests

History

• 💔 Build #3963 failed 04b46c6
• 💔 Build #3956 failed cc31660
• 💔 Build #3951 failed 36ee90c
• 💔 Build #3947 failed b23ea7b

cc @jfreden

💔 Build Failed

• Buildkite Build
• Commit: 94c9871

Failed CI Steps

• :windows: Unit Tests / family/core-windows-2016
• :windows: Unit Tests / family/core-windows-2022

History

• 💔 Build #2610 failed 04b46c6
• 💔 Build #2603 failed cc31660
• 💔 Build #2598 failed 36ee90c
• 💔 Build #2594 failed b23ea7b

cc @jfreden

@miltonhultgren this is my first beats PR. Is it expected that windows/Unit tests and x-pack/dockerlogbeat Load dynamic pipeline's steps fail on the branch build?

@jfreden Hi! Any build step that is from Buildkite is safe to ignore for now (it's in the middle of a migration).

Your build looks successful other than that so feel free to merge!